v50.0.0

Compare Source

GENERAL

▶ [MAJOR] #​6213
The Generic Worker Docker Engine was an experimental engine that was never used
in production. It was an intended starting point for adding support for
docker-worker style payloads. However, a new approach to running Docker Worker
payloads in the multiuser engine was agreed, and is under active
development. This will
provide the same functionality that the Docker Engine was intended to provide.
Therefore the old, incomplete, and unused docker engine has been removed.

▶ [patch] #​6216
Build freebsd versions of livelog, taskcluster-proxy and start-worker to complement the existing generic-worker builds.

USERS

▶ [patch] #​6208
Return a malformed payload error if payload.features.interactive is enabled in the task definition, while the enableInteractive worker config is false.

DEVELOPERS

▶ [patch]
jsonschema2go cli now has options for generating nested structs, and including default values as struct tags.

v49.2.0

Compare Source

GENERAL

▶ [patch]
Upgrade Node.js version to 18.16.0 and go version to 1.19.9.

USERS

▶ [minor] #​6169
Adds interactive shell support to generic-worker.

The worker configuration variable enableInteractive needs to be set to true to allow the interactive shell feature to be enabled. enableInteractive is disabled by default.

Once the worker configuration variable is set, the interactive feature can be enabled on a per-task basis.

To enable, set task.payload.features.interactive to true. And toggle on Interactive in the Create Task view of the UI.

v49.1.3

Compare Source

WORKER-DEPLOYERS

▶ [patch] #​6186
Worker-manager refreshes worker from database before calling removeWorker on terminateAfter time exceeded to prevent from stopping workers that were already registered and running since worker scanner has started.

v49.1.2

Compare Source

USERS

▶ [patch] #​6185
Fixed quarantine worker 'reason' field schema to be optional.

▶ [patch] #​6058
Generic Worker no longer modifies the Access Control Lists of the Interactive Desktop and the associated Windows Station unless additional OS groups have been specified in the task payload osGroups property. Previously Generic Worker would modify the ACLs of these objects even if the access token it was using for launching task command processes already had suitable permissions. This patch is a workaround for a more general issue, which is that the ACL modifications seem not to be appropriate in all cases when a new access token is needed. See https://bugzilla.mozilla.org/show_bug.cgi?id=1815711.

There is a likely to be a follow up fix for the ACL modifications that occur when a new access token is required, once it is understood why the current modifications are not always sufficient.

v49.1.1

Compare Source

GENERAL

▶ [patch]
Generic worker feature task.Payload.OnExitStatus.PurgeCaches now only purges caches related to the task, instead of all caches on the worker.

USERS

▶ [patch] #​5773
Fix UI bug when user profile was missing and causing whole page to crash.

▶ [patch] bug 1590886
Github status handler listens to both taskPending and taskRunning events.

v49.1.0

Compare Source

ADMINS

▶ [minor] bug 1826417
Changes the way expire-artifacts works. It uses a separate function to fetch all expired artifacts and then uses bulk delete to remove them from S3 and the database.